-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
#2927: Blocked from starting a new domain request when there are other started domain requests - [MEOWARD] #3017
Conversation
Doesn't account for clicking the button after page refresh
This reverts commit f4c6c08.
🥳 Successfully deployed to developer sandbox za. |
🥳 Successfully deployed to developer sandbox za. |
🥳 Successfully deployed to developer sandbox za. |
🥳 Successfully deployed to developer sandbox za. |
🥳 Successfully deployed to developer sandbox za. |
🥳 Successfully deployed to developer sandbox za. |
🥳 Successfully deployed to developer sandbox za. |
🥳 Successfully deployed to developer sandbox za. |
🥳 Successfully deployed to developer sandbox za. |
🥳 Successfully deployed to developer sandbox za. |
🥳 Successfully deployed to developer sandbox za. |
🥳 Successfully deployed to developer sandbox za. |
🥳 Successfully deployed to developer sandbox za. |
🥳 Successfully deployed to developer sandbox za. |
🥳 Successfully deployed to developer sandbox za. |
1 similar comment
🥳 Successfully deployed to developer sandbox za. |
🥳 Successfully deployed to developer sandbox za. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Verified and tested ACs + code LGTM! Just had two small questions and can approve afterwards
domain_request_urls = [ | ||
path("", views.DomainRequestWizard.as_view(), name=""), | ||
path("", RedirectView.as_view(pattern_name="domain-request:start"), name="redirect-to-start"), | ||
path("start/", views.DomainRequestWizard.as_view(), name="start"), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice!
@@ -182,7 +183,9 @@ def configure_step_options(self): | |||
|
|||
def has_pk(self): | |||
"""Does this wizard know about a DomainRequest database record?""" | |||
return "domain_request_id" in self.storage | |||
if self.kwargs.get("id") is not None: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
does this work the same if we one liner this to return self.kwargs.get("id")
or return self.kwargs.get("id") is not None
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great suggestion! The is not None one liner should return the same thing
@@ -493,6 +493,7 @@ def get_context_data(self): | |||
# Hides the requests and domains buttons in the navbar | |||
context_stuff["hide_requests"] = self.is_portfolio | |||
context_stuff["hide_domains"] = self.is_portfolio | |||
context_stuff["domain_request_id"] = self.domain_request.id |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know this is for pre-existing code not in scope, but thoughts on renaming this variable to form_context
or something along the lines of that?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What do you think about context
? I'm not opposed to doing that, I was thinking the same thing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think just context also works! Glad we were in agreement 🎉
🥳 Successfully deployed to developer sandbox za. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! 🚢
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Ticket
Resolves #2927
Changes
Context for reviewers
Context for design:
The only design change is a breadcrumb on the first page of the domain request flow. This exists on the non-org view as well.
General context:
This bug was happening because the original DomainRequestWizard was actually storing the domain request id and the "new_request" variable in the session. Because our session is in our database as a CacheTable, this meant that you could override the session state by taking other actions in another tab.
The fix for this is to simply expose the domain request id in the actual url itself, rather than relying on session to store this information for us.
Because we are now removing the id, this does reintroduce the back button bug. It was decided that this would be resolved with a new design, so a breadcrumb has also been added to the first step of the domain request flow.
Setup
(devs only) You can reproduce the original bug on another sandbox by doing the following:
For this ticket, follow these same steps on getgov-meoward. This behavior should now no longer exist.
To test the new breadcrumb (both portfolio and non portfolio:
Code Review Verification Steps
As the original developer, I have
Satisfied acceptance criteria and met development standards
Ensured code standards are met (Original Developer)
Validated user-facing changes (if applicable)
As a code reviewer, I have
Reviewed, tested, and left feedback about the changes
Validated user-facing changes as a developer
Note: Multiple code reviewers can share the checklists above, a second reviewer should not make a duplicate checklist. All checks should be checked before approving, even those labeled N/A.
As a designer reviewer, I have
Verified that the changes match the design intention
Validated user-facing changes as a designer
References
Screenshots